Fetch

Goals

The goal is to unify fetching across the web platform and provide consistent handling of everything that involves, including:

• URL schemes
• Redirects
• Cross-origin semantics
• CSP [CSP]
• Service workers [SW]
• Mixed Content [MIX]
• `Referer` [REFERRER]

To do so it also supersedes the HTTP `Origin` header semantics originally defined in The Web Origin Concept. [ORIGIN]

1. Preface

At a high level, fetching a resource is a fairly simple operation. A request goes in, a response comes out. The details of that operation are however quite involved and used to not be written down carefully and differ from one API to the next.

Numerous APIs provide the ability to fetch a resource, e.g. HTML’s img and script element, CSS' cursor and list-style-image, the navigator.sendBeacon() and self.importScripts() JavaScript APIs. The Fetch Standard provides a unified architecture for these features so they are all consistent when it comes to various aspects of fetching, such as redirects and the CORS protocol.

The Fetch Standard also defines the fetch() JavaScript API, which exposes most of the networking functionality at a fairly low level of abstraction.

2. Infrastructure

This specification depends on the Infra Standard. [INFRA]

This specification uses terminology from the ABNF, Encoding, HTML, HTTP, IDL, MIME Sniffing, Streams, and URL Standards. [ABNF] [ENCODING] [HTML] [HTTP] [WEBIDL] [MIMESNIFF] [STREAMS] [URL]

ABNF means ABNF as augmented by HTTP (in particular the addition #) and RFC 7405. [RFC7405]

Credentials are HTTP cookies, TLS client certificates, and authentication entries (for HTTP authentication). [COOKIES] [TLS] [HTTP-AUTH]

Tasks that are queued by this standard are annotated as one of:

• process request body
• process request end-of-body
• process response
• process response end-of-body
• process response done

To queue a fetch task on request request to run an operation, run these steps:

1. If request’s client is null, terminate these steps.

2. Queue a task to run an operation on request’s client’s responsible event loop using the networking task source.

To queue a fetch-request-done task, given a request, queue a fetch task on request to process request end-of-body for request.

To serialize an integer, represent it as a string of the shortest possible decimal number.

This will be replaced by a more descriptive algorithm in Infra. See infra/201.

2.1. URL

A local scheme is a scheme that is "about", "blob", or "data".

A URL is local if its scheme is a local scheme.

This definition is also used by Referrer Policy. [REFERRER]

An HTTP(S) scheme is a scheme that is "http" or "https".

A network scheme is a scheme that is "ftp" or an HTTP(S) scheme.

A fetch scheme is a scheme that is "about", "blob", "data", "file", or a network scheme.

HTTP(S) scheme, network scheme, and fetch scheme are also used by HTML. [HTML]

A response URL is a URL for which implementations need not store the fragment as it is never exposed. When serialized, the exclude fragment flag is set, meaning implementations can store the fragment nonetheless.

2.2. HTTP

While fetching encompasses more than just HTTP, it borrows a number of concepts from HTTP and applies these to resources obtained via other means (e.g., data URLs).

An HTTP tab or space is U+0009 TAB or U+0020 SPACE.

HTTP whitespace is U+000A LF, U+000D CR, or an HTTP tab or space.

HTTP whitespace is only useful for specific constructs that are reused outside the context of HTTP headers (e.g., MIME types). For HTTP header values, using HTTP tab or space is preferred, and outside that context ASCII whitespace is preferred. Unlike ASCII whitespace this excludes U+000C FF.

An HTTP newline byte is 0x0A (LF) or 0x0D (CR).

An HTTP tab or space byte is 0x09 (HT) or 0x20 (SP).

An HTTP whitespace byte is an HTTP newline byte or HTTP tab or space byte.

An HTTPS state value is "none", "deprecated", or "modern".

A response delivered over HTTPS will typically have its HTTPS state set to "modern". A user agent can use "deprecated" in a transition period. E.g., while removing support for a hash function, weak cipher suites, certificates for an "Internal Name", or certificates with an overly long validity period. How exactly a user agent can use "deprecated" is not defined by this specification. An environment settings object typically derives its HTTPS state from a response.

To collect an HTTP quoted string from a string input, given a position variable position and optionally an extract-value flag, run these steps:

1. Let positionStart be position.

2. Let value be the empty string.

3. Assert: the code point at position within input is U+0022 (").

4. Advance position by 1.

5. While true:

   1. Append the result of collecting a sequence of code points that are not U+0022 (") or U+005C (\) from input, given position, to value.

   2. If position is past the end of input, then break.

   3. Let quoteOrBackslash be the code point at position within input.

   4. Advance position by 1.

   5. If quoteOrBackslash is U+005C (\), then:

      1. If position is past the end of input, then append U+005C (\) to value and break.

      2. Append the code point at position within input to value.

      3. Advance position by 1.

   6. Otherwise:

      1. Assert: quoteOrBackslash is U+0022 (").

      2. Break.

6. If the extract-value flag is set, then return value.

7. Return the code points from positionStart to position, inclusive, within input.

The extract-value flag argument makes this algorithm suitable for getting, decoding, and splitting and parse a MIME type, as well as other header value parsers that might need this.

2.2.1. Methods

A method is a byte sequence that matches the method token production.

A CORS-safelisted method is a method that is `GET`, `HEAD`, or `POST`.

A forbidden method is a method that is a byte-case-insensitive match for `CONNECT`, `TRACE`, or `TRACK`. [HTTPVERBSEC1], [HTTPVERBSEC2], [HTTPVERBSEC3]

To normalize a method, if it is a byte-case-insensitive match for `DELETE`, `GET`, `HEAD`, `OPTIONS`, `POST`, or `PUT`, byte-uppercase it.

Normalization is done for backwards compatibility and consistency across APIs as methods are actually "case-sensitive".

Using `patch` is highly likely to result in a `405 Method Not Allowed`. `PATCH` is much more likely to succeed.

There are no restrictions on methods. `CHICKEN` is perfectly acceptable (and not a misspelling of `CHECKIN`). Other than those that are normalized there are no casing restrictions either. `Egg` or `eGg` would be fine, though uppercase is encouraged for consistency.

2.2.2. Headers

A header list is a list of zero or more headers. It is initially the empty list.

A header list is essentially a specialized multimap. An ordered list of key-value pairs with potentially duplicate keys.

To get a structured field value given a name and a type from a header list list, run these steps:

1. Assert: type is one of "dictionary", "list", or "item".

2. Let value be the result of getting name from list.

3. If value is null, then return null.

4. Let result be the result of parsing structured fields with input_string set to value and header_type set to type.

5. If parsing failed, then return null.

6. Return result.

Get a structured field value intentionally does not distinguish between a header not being present and its value failing to parse as a structured field value. This ensures uniform processing across the web platform.

To set a structured field value name/structured field value name/structuredValue pair in a header list list, run these steps:

1. Let serializedValue be the result of executing the serializing structured fields algorithm on structuredValue.

2. Set name/serializedValue in list.

Structured field values are defined as objects which HTTP can (eventually) serialize in interesting and efficient ways. For the moment, Fetch only supports header values as byte sequences, which means that these objects can be set in header lists only via serialization, and they can be obtained from header lists only by parsing. In the future the fact that they are objects might be preserved end-to-end. [HEADER-STRUCTURE]

A header list list contains a name name if list contains a header whose name is a byte-case-insensitive match for name.

To get a name name from a header list list, run these steps:

1. If list does not contain name, then return null.

2. Return the values of all headers in list whose name is a byte-case-insensitive match for name, separated from each other by 0x2C 0x20, in order.

To get, decode, and split a name name from header list list, run these steps:

1. Let initialValue be the result of getting name from list.

2. If initialValue is null, then return null.

3. Let input be the result of isomorphic decoding initialValue.

4. Let position be a position variable for input, initially pointing at the start of input.

5. Let values be a list of strings, initially empty.

6. Let value be the empty string.

7. While position is not past the end of input:

   1. Append the result of collecting a sequence of code points that are not U+0022 (") or U+002C (,) from input, given position, to value.

      The result might be the empty string.

   2. If position is not past the end of input, then:

      1. If the code point at position within input is U+0022 ("), then:

         1. Append the result of collecting an HTTP quoted string from input, given position, to value.

         2. If position is not past the end of input, then continue.

      2. Otherwise:

         1. Assert: the code point at position within input is U+002C (,).

         2. Advance position by 1.

   3. Remove all HTTP tab or space from the start and end of value.

   4. Append value to values.

   5. Set value to the empty string.

8. Return values.

A: nosniff,

A: nosniff
B: sniff
A:

A: text/html;", x/x

A: text/html;"
A: x/x

A: x/x;test="hi",y/y

A: x/x;test="hi"
C: **bingo**
A: y/y

A: x / x,,,1

A: x / x
A: ,
A: 1

A: "1,2", 3

A: "1,2"
D: 4
A: 3

To append a name/value name/value pair to a header list list, run these steps:

1. If list contains name, then set name to the first such header’s name.

   This reuses the casing of the name of the header already in list, if any. If there are multiple matched headers their names will all be identical.

2. Append a new header whose name is name and value is value to list.

To delete a name name from a header list list, remove all headers whose name is a byte-case-insensitive match for name from list.

To set a name/value name/value pair in a header list list, run these steps:

1. If list contains name, then set the value of the first such header to value and remove the others.

2. Otherwise, append a new header whose name is name and value is value to list.

To combine a name/value name/value pair in a header list list, run these steps:

1. If list contains name, then set the value of the first such header to its value, followed by 0x2C 0x20, followed by value.

2. Otherwise, append a new header whose name is name and value is value to list.

Combine is used by XMLHttpRequest and the WebSocket protocol handshake.

To convert header names to a sorted-lowercase set, given a list of names headerNames, run these steps:

1. Let headerNamesSet be a new ordered set.

2. For each name of headerNames, append the result of byte-lowercasing name to headerNamesSet.

3. Return the result of sorting headerNamesSet in ascending order with byte less than.

To sort and combine a header list list, run these steps:

1. Let headers be an empty list of name-value pairs with the key being the name and value the value.

2. Let names be the result of convert header names to a sorted-lowercase set with all the names of the headers in list.

3. For each name in names:

   1. Let value be the result of getting name from list.

   2. Assert: value is not null.

   3. Append name-value to headers.

4. Return headers.

A header consists of a name and value.

A name is a byte sequence that matches the field-name token production.

A value is a byte sequence that matches the following conditions:

• Has no leading or trailing HTTP tab or space bytes.

• Contains no 0x00 (NUL) or HTTP newline bytes.

The definition of value is not defined in terms of an HTTP token production as it is broken.

To normalize a potentialValue, remove any leading and trailing HTTP whitespace bytes from potentialValue.

To determine whether a header header is a CORS-safelisted request-header, run these steps:

1. Let value be header’s value.

2. Byte-lowercase header’s name and switch on the result:

   `accept`

   If value contains a CORS-unsafe request-header byte, then return false.

   `accept-language`

   `content-language`

   If value contains a byte that is not in the range 0x30 (0) to 0x39 (9), inclusive, is not in the range 0x41 (A) to 0x5A (Z), inclusive, is not in the range 0x61 (a) to 0x7A (z), inclusive, and is not 0x20 (SP), 0x2A (*), 0x2C (,), 0x2D (-), 0x2E (.), 0x3B (;), or 0x3D (=), then return false.

   `content-type`

   1. If value contains a CORS-unsafe request-header byte, then return false.

   2. Let mimeType be the result of parsing value.

   3. If mimeType is failure, then return false.

   4. If mimeType’s essence is not "application/x-www-form-urlencoded", "multipart/form-data", or "text/plain", then return false.

   This intentionally does not use extract a MIME type as that algorithm is rather forgiving and servers are not expected to implement it.

   If extract a MIME type were used the following request would not result in a CORS preflight and a naïve parser on the server might treat the request body as JSON:

   fetch("https://victim.example/naïve-endpoint", {
     method: "POST",
     headers: [
       ["Content-Type", "application/json"],
       ["Content-Type", "text/plain"]
     ],
     credentials: "include",
     body: JSON.stringify(exerciseForTheReader)
   });
   

   Otherwise

   Return false.

3. If value’s length is greater than 128, then return false.

4. Return true.

There are limited exceptions to the `Content-Type` header safelist, as documented in CORS protocol exceptions.

A CORS-unsafe request-header byte is a byte byte for which one of the following is true:

• byte is less than 0x20 and is not 0x09 HT

• byte is 0x22 ("), 0x28 (left parenthesis), 0x29 (right parenthesis), 0x3A (:), 0x3C (<), 0x3E (>), 0x3F (?), 0x40 (@), 0x5B ([), 0x5C (\), 0x5D (]), 0x7B ({), 0x7D (}), or 0x7F DEL.

The CORS-unsafe request-header names, given a header list headers, are determined as follows:

1. Let unsafeNames be a new list.

2. Let potentiallyUnsafeNames be a new list.

3. Let safelistValueSize be 0.

4. For each header of headers:

   1. If header is not a CORS-safelisted request-header, then append header’s name to unsafeNames.

   2. Otherwise, append header’s name to potentiallyUnsafeNames and increase safelistValueSize by header’s value’s length.

5. If safelistValueSize is greater than 1024, then for each name of potentiallyUnsafeNames, append name to unsafeNames.

6. Return the result of convert header names to a sorted-lowercase set with unsafeNames.

A CORS non-wildcard request-header name is a byte-case-insensitive match for `Authorization`.

A privileged no-CORS request-header name is a header name that is a byte-case-insensitive match for one of

• `Range`.

A CORS-safelisted response-header name, given a CORS-exposed header-name list list, is a header name that is a byte-case-insensitive match for one of

• `Cache-Control`
• `Content-Language`
• `Content-Length`
• `Content-Type`
• `Expires`
• `Last-Modified`
• `Pragma`
• Any value in list that is not a forbidden response-header name.

A no-CORS-safelisted request-header name is a header name that is a byte-case-insensitive match for one of

• `Accept`
• `Accept-Language`
• `Content-Language`
• `Content-Type`

To determine whether a header header is a no-CORS-safelisted request-header, run these steps:

1. If header’s name is not a no-CORS-safelisted request-header name, then return false.

2. Return whether header is a CORS-safelisted request-header.

A forbidden header name is a header name that is a byte-case-insensitive match for one of

• `Accept-Charset`
• `Accept-Encoding`
• `Access-Control-Request-Headers`
• `Access-Control-Request-Method`
• `Connection`
• `Content-Length`
• `Cookie`
• `Cookie2`
• `Date`
• `DNT`
• `Expect`
• `Host`
• `Keep-Alive`
• `Origin`
• `Referer`
• `TE`
• `Trailer`
• `Transfer-Encoding`
• `Upgrade`
• `Via`

or a header name that starts with a byte-case-insensitive match for `Proxy-` or `Sec-` (including being a byte-case-insensitive match for just `Proxy-` or `Sec-`).

These are forbidden so the user agent remains in full control over them. Names starting with `Sec-` are reserved to allow new headers to be minted that are safe from APIs using fetch that allow control over headers by developers, such as XMLHttpRequest. [XHR]

A forbidden response-header name is a header name that is a byte-case-insensitive match for one of:

• `Set-Cookie`
• `Set-Cookie2`

A request-body-header name is a header name that is a byte-case-insensitive match for one of:

• `Content-Encoding`
• `Content-Language`
• `Content-Location`
• `Content-Type`

To extract header values given a header header, run these steps:

1. If parsing header’s value, per the ABNF for header’s name, fails, then return failure.

2. Return one or more values resulting from parsing header’s value, per the ABNF for header’s name.

To extract header list values given a name name and a header list list, run these steps:

1. If list does not contain name, then return null.

2. If the ABNF for name allows a single header and list contains more than one, then return failure.

   If different error handling is needed, extract the desired header first.

3. Let values be an empty list.

4. For each header header list contains whose name is name:

   1. Let extract be the result of extracting header values from header.

   2. If extract is failure, then return failure.

   3. Append each value in extract, in order, to values.

5. Return values.

A default `User-Agent` value is a user-agent-defined value for the `User-Agent` header.

2.2.3. Statuses

A status is a code.

A null body status is a status that is 101, 204, 205, or 304.

An ok status is any status in the range 200 to 299, inclusive.

A redirect status is a status that is 301, 302, 303, 307, or 308.

2.2.4. Bodies

A body consists of:

• A stream (null or a ReadableStream object).

• A transmitted bytes (an integer), initially 0.

• A total bytes (an integer), initially 0.

• A source, initially null.

A body body is said to be done if body is null or body’s stream is closed or errored.

To wait for a body body, wait for body to be done.

To clone a body body, run these steps:

1. Let «out1, out2» be the result of teeing body’s stream.

2. Set body’s stream to out1.

3. Return a body whose stream is out2 and other members are copied from body.

To handle content codings given codings and bytes, run these steps:

1. If codings are not supported, then return bytes.

2. Return the result of decoding bytes with codings as explained in HTTP, if decoding does not result in an error, and failure otherwise. [HTTP] [HTTP-SEMANTICS]

2.2.5. Requests

The input to fetch is a request.

A request has an associated method (a method). Unless stated otherwise it is `GET`.

This can be updated during redirects to `GET` as described in HTTP fetch.

A request has an associated URL (a URL).

Implementations are encouraged to make this a pointer to the first URL in request’s URL list. It is provided as a distinct field solely for the convenience of other standards hooking into Fetch.

A request has an associated local-URLs-only flag. Unless stated otherwise it is unset.

A request has an associated header list (a header list). Unless stated otherwise it is empty.

A request has an associated unsafe-request flag. Unless stated otherwise it is unset.

The unsafe-request flag is set by APIs such as fetch() and XMLHttpRequest to ensure a CORS-preflight fetch is done based on the supplied method and header list. It does not free an API from outlawing forbidden methods and forbidden header names.

A request has an associated body (null or a body). Unless stated otherwise it is null.

This can be updated during redirects to null as described in HTTP fetch.

A request has an associated client (null or an environment settings object).

A request has an associated reserved client (null, an environment, or an environment settings object). Unless stated otherwise it is null.

This is only used by navigation requests and worker requests, but not service worker requests. It references an environment for a navigation request and an environment settings object for a worker request.

A request has an associated replaces client id (a string). Unless stated otherwise it is the empty string.

This is only used by navigation requests. It is the id of the target browsing context’s active document’s environment settings object.

A request has an associated window ("no-window", "client", or an environment settings object whose global object is a Window object). Unless stated otherwise it is "client".

The "client" value is changed to "no-window" or request’s client during fetching. It provides a convenient way for standards to not have to explicitly set request’s window.

A request has an associated keepalive flag. Unless stated otherwise it is unset.

This can be used to allow the request to outlive the environment settings object, e.g., navigator.sendBeacon and the HTML img element set this flag. Requests with this flag set are subject to additional processing requirements.

A request has an associated service-workers mode, that is "all" or "none". Unless stated otherwise it is "all".

A request has an associated initiator, which is the empty string, "download", "imageset", "manifest", "prefetch", "prerender", or "xslt". Unless stated otherwise it is the empty string.

A request’s initiator is not particularly granular for the time being as other specifications do not require it to be. It is primarily a specification device to assist defining CSP and Mixed Content. It is not exposed to JavaScript. [CSP] [MIX]

A request has an associated destination, which is the empty string, "audio", "audioworklet", "document", "embed", "font", "frame", "iframe", "image", "manifest", "object", "paintworklet", "report", "script", "serviceworker", "sharedworker", "style", "track", "video", "worker", or "xslt". Unless stated otherwise it is the empty string.

A request’s destination is script-like if it is "audioworklet", "paintworklet", "script", "serviceworker", "sharedworker", or "worker".

Algorithms that use script-like should also consider "xslt" as that too can cause script execution. It is not included in the list as it is not always relevant and might require different behavior.

A request has an associated priority (null or a user-agent-defined object). Unless otherwise stated it is null.

A request has an associated origin, which is "client" or an origin. Unless stated otherwise it is "client".

"client" is changed to an origin during fetching. It provides a convenient way for standards to not have to set request’s origin.

A request has an associated referrer, which is "no-referrer", "client", or a URL. Unless stated otherwise it is "client".

"client" is changed to "no-referrer" or a URL during fetching. It provides a convenient way for standards to not have to set request’s referrer.

A request has an associated referrer policy, which is a referrer policy. Unless stated otherwise it is the empty string. [REFERRER]

This can be used to override a referrer policy associated with an environment settings object.

A request has an associated synchronous flag. Unless stated otherwise it is unset.

A request has an associated mode, which is "same-origin", "cors", "no-cors", "navigate", or "websocket". Unless stated otherwise, it is "no-cors".

A request has an associated use-CORS-preflight flag. Unless stated otherwise, it is unset.

The use-CORS-preflight flag being set is one of several conditions that results in a CORS-preflight request. The use-CORS-preflight flag is set if either one or more event listeners are registered on an XMLHttpRequestUpload object or if a ReadableStream object is used in a request.

A request has an associated credentials mode, which is "omit", "same-origin", or "include". Unless stated otherwise, it is "omit".

A request has an associated use-URL-credentials flag. Unless stated otherwise, it is unset.

A request has an associated cache mode, which is "default", "no-store", "reload", "no-cache", "force-cache", or "only-if-cached". Unless stated otherwise, it is "default".

A request has an associated redirect mode, which is "follow", "error", or "manual". Unless stated otherwise, it is "follow".

A request has associated integrity metadata (a string). Unless stated otherwise, it is the empty string.

A request has associated cryptographic nonce metadata (a string). Unless stated otherwise, it is the empty string.

A request has associated parser metadata which is the empty string, "parser-inserted", or "not-parser-inserted". Unless otherwise stated, it is the empty string.

A request’s cryptographic nonce metadata and parser metadata are generally populated from attributes and flags on the HTML element responsible for creating a request. They are used by various algorithms in Content Security Policy to determine whether requests or responses are to be blocked in a given context. [CSP]

A request has an associated reload-navigation flag. Unless stated otherwise, it is unset.

This flag is for exclusive use by HTML’s navigate algorithm. [HTML]

A request has an associated history-navigation flag. Unless stated otherwise, it is unset.

This flag is for exclusive use by HTML’s navigate algorithm. [HTML]

A request has an associated tainted origin flag. Unless stated otherwise, it is unset.

A request has an associated URL list (a list of one or more URLs). Unless stated otherwise, it is a list containing a copy of request’s URL.

A request has an associated current URL. It is a pointer to the last URL in request’s URL list.

A request has an associated redirect count. Unless stated otherwise, it is zero.

A request has an associated response tainting, which is "basic", "cors", or "opaque". Unless stated otherwise, it is "basic".

A request has an associated prevent no-cache cache-control header modification flag. Unless stated otherwise, it is unset.

A request has an associated done flag. Unless stated otherwise, it is unset.

A request has an associated timing allow failed flag. Unless stated otherwise, it is unset.

A request’s tainted origin flag, URL list, current URL, redirect count, response tainting, done flag, and timing allow failed flag are used as bookkeeping details by the fetch algorithm.

A subresource request is a request whose destination is "audio", "audioworklet", "font", "image", "manifest", "paintworklet", "script", "style", "track", "video", "xslt", or the empty string.

A non-subresource request is a request whose destination is "document", "embed", "frame", "iframe", "object", "report", "serviceworker", "sharedworker", or "worker".

A navigation request is a request whose destination is "document", "embed", "frame", "iframe", or "object".

See handle fetch for usage of these terms. [SW]

Serializing a request origin, given a request request, is to run these steps:

1. If request’s tainted origin flag is set, then return "null".

2. Return request’s origin, serialized.

Byte-serializing a request origin, given a request request, is to return the result of serializing a request origin with request, isomorphic encoded.

To clone a request request, run these steps:

1. Let newRequest be a copy of request, except for its body.

2. If request’s body is non-null, set newRequest’s body to the result of cloning request’s body.

3. Return newRequest.

To transmit body for a request request, run these steps:

1. Let body be request’s body.

2. If body is null, then queue a fetch task on request to process request end-of-body for request and abort these steps.

3. Let reader be the result of getting a reader from body’s stream.

   This operation cannot throw an exception.

4. Perform the transmit-body loop given request, body, and reader.

To perform the transmit-body loop given request, body, and reader:

1. Let readRequest be the following read request:

   chunk steps, given chunk

   1. If the ongoing fetch is terminated, then abort these steps.

   2. If chunk is not a Uint8Array object, terminate the ongoing fetch and abort these steps.

   3. Let bs be the byte sequence represented by the Uint8Array object.

   4. In parallel:

      1. Transmit bs. Whenever one or more bytes are transmitted, increase body’s transmitted bytes by the number of transmitted bytes and queue a fetch task on request to process request body for request.

         This step blocks until bs is fully transmitted.

      2. If the ongoing fetch is not terminated, then queue a fetch task on request to perform the transmit-body loop given request, body, and reader.

   close steps

   1. If the ongoing fetch is terminated, then abort these steps.

   2. Queue a fetch task on request to process request end-of-body for request.

   error steps, given e

   1. If the ongoing fetch is terminated, then abort these steps.

   2. If e is an "AbortError" DOMException, then terminate the ongoing fetch with the aborted flag set.

   3. Otherwise, terminate the ongoing fetch.

2. Read a chunk from body’s stream with reader given readRequest.

To add a range header to a request request, with an integer first, and an optional integer last, run these steps:

1. Let rangeValue be `bytes `.

2. Serialize and isomorphic encode first, and append the result to rangeValue.

3. Append 0x2D (-) to rangeValue.

4. If last is given, then serialize and isomorphic encode it, and append the result to rangeValue.

5. Append `Range`/rangeValue to request’s header list.

A range header denotes an inclusive byte range. There a range header where first is 0 and last is 500, is a range of 501 bytes.

Features that combine multiple responses into one logical resource are historically a source of security bugs. Please seek security review for features that deal with partial responses.

To serialize a response URL for reporting, given a response response, run these steps:

1. Assert: response’s URL list is not empty.

2. Let url be a copy of response’s URL list’s first element.

   This is not response’s URL in order to avoid leaking information about redirect targets (see similar considerations for CSP reporting too). [CSP]

3. Set the username given url and the empty string.

4. Set the password given url and the empty string.

5. Return the serialization of url with the exclude fragment flag set.

2.2.6. Responses

The result of fetch is a response. A response evolves over time. That is, not all its fields are available straight away.

A response has an associated type which is "basic", "cors", "default", "error", "opaque", or "opaqueredirect". Unless stated otherwise, it is "default".

A response can have an associated aborted flag, which is initially unset.

This indicates that the request was intentionally aborted by the developer or end-user.

A response has an associated URL. It is a pointer to the last response URL in response’s URL list and null if response’s URL list is the empty list.

A response has an associated URL list (a list of zero or more response URLs). Unless stated otherwise, it is the empty list.

Except for the last response URL, if any, a response’s URL list cannot be exposed to script. That would violate atomic HTTP redirect handling.

A response has an associated status, which is a status. Unless stated otherwise it is 200.

A response has an associated status message. Unless stated otherwise it is the empty byte sequence.

Responses over an HTTP/2 connection will always have the empty byte sequence as status message as HTTP/2 does not support them.

A response has an associated header list (a header list). Unless stated otherwise it is empty.

A response has an associated body (null or a body). Unless stated otherwise it is null.

A response has an associated cache state (the empty string or "local"). Unlesss stated otherwise, it is the empty string.

This is intended solely for usage by service workers. [SW]

A response has an associated HTTPS state (an HTTPS state value). Unless stated otherwise, it is "none".

A response has an associated CSP list, which is a list of Content Security Policy objects for the response. The list is empty unless otherwise specified. [CSP]

A response has an associated CORS-exposed header-name list (a list of zero or more header names). The list is empty unless otherwise specified.

A response will typically get its CORS-exposed header-name list set by extracting header values from the `Access-Control-Expose-Headers` header. This list is used by a CORS filtered response to determine which headers to expose.

A response has an associated range-requested flag, which is initially unset.

This is used to ensure to prevent a partial response from an earlier ranged request being provided to an API that didn’t make a range request. See the flag’s usage for a detailed description of the attack.

A response has an associated timing allow passed flag, which is initially unset.

This is used so that the caller to a fetch can determine if sensitive timing data is allowed on the resource fetched by looking at the flag of the response returned. Because the flag on the response of a redirect has to be set if it was set for previous responses in the redirect chain, this is also tracked internally using the request’s timing allow failed flag.

A response can have an associated location URL (null, failure, or a URL). Unless specified otherwise, response has no location URL.

This concept is used for redirect handling in Fetch and in HTML’s navigate algorithm. It ensures `Location` has its value extracted consistently and only once. [HTML]

A response whose type is "error" and aborted flag is set is known as an aborted network error.

A response whose type is "error" is known as a network error.

A network error is a response whose status is always 0, status message is always the empty byte sequence, header list is always empty, and body is always null.

A filtered response is a limited view on a response that is not a network error. This response is referred to as the filtered response’s associated internal response.

The fetch algorithm returns such a view to ensure APIs do not accidentally leak information. If the information needs to be exposed for legacy reasons, e.g., to feed image data to a decoder, the associated internal response can be used, which is only "accessible" to internal specification algorithms and is never a filtered response itself.

A basic filtered response is a filtered response whose type is "basic" and header list excludes any headers in internal response’s header list whose name is a forbidden response-header name.

A CORS filtered response is a filtered response whose type is "cors" and header list excludes any headers in internal response’s header list whose name is not a CORS-safelisted response-header name, given internal response’s CORS-exposed header-name list.

An opaque filtered response is a filtered response whose type is "opaque", URL list is the empty list, status is 0, status message is the empty byte sequence, header list is empty, and body is null.

An opaque-redirect filtered response is a filtered response whose type is "opaqueredirect", status is 0, status message is the empty byte sequence, header list is empty, and body is null.

To clone a response response, run these steps:

1. If response is a filtered response, then return a new identical filtered response whose internal response is a clone of response’s internal response.

2. Let newResponse be a copy of response, except for its body.

3. If response’s body is non-null, then set newResponse’s body to the result of cloning response’s body.

4. Return newResponse.

A fresh response is a response whose current age is within its freshness lifetime.

A stale-while-revalidate response is a response that is not a fresh response and whose current age is within the stale-while-revalidate lifetime.

A stale response is a response is a response that is not a fresh response or a stale-while-revalidate response.

2.2.7. Miscellaneous

A potential destination is "fetch" or a destination which is not the empty string.

To translate a potential destination potentialDestination, run these steps:

1. If potentialDestination is "fetch", then return the empty string.

2. Assert: potentialDestination is a destination.

3. Return potentialDestination.

2.3. Authentication entries

An authentication entry and a proxy-authentication entry are tuples of username, password, and realm, used for HTTP authentication and HTTP proxy authentication, and associated with one or more requests.

User agents should allow both to be cleared together with HTTP cookies and similar tracking functionality.

Further details are defined by HTTP. [HTTP] [HTTP-SEMANTICS] [HTTP-COND] [HTTP-CACHING] [HTTP-AUTH]

2.4. Fetch groups

Each environment settings object has an associated fetch group.

A fetch group holds an ordered list of fetch records.

A fetch record has an associated request (a request).

A fetch record has an associated fetch (a fetch algorithm or null).

When a fetch group is terminated, for each associated fetch record whose request’s done flag or keepalive flag is unset, terminate the fetch record’s fetch.

2.5. Connections

A user agent has an associated connection pool. A connection pool consists of zero or more connections. Each connection is identified by an origin (an origin) and credentials (a boolean).

To obtain a connection, given an origin and credentials, run these steps:

1. If connection pool contains a connection whose origin is origin and credentials is credentials, then return that connection.

2. Let connection be null.

3. Run these steps, but abort when the ongoing fetch is terminated:

   1. Set connection to the result of establishing an HTTP connection to origin. [HTTP] [HTTP-SEMANTICS] [HTTP-COND] [HTTP-CACHING] [HTTP-AUTH] [TLS]

      If credentials is false, then do not send a TLS client certificate.

      If establishing a connection does not succeed (e.g., a DNS, TCP, or TLS error), then return failure.

4. If aborted, then:

   1. If connection is not null, then close connection.

   2. Return failure.

5. Add connection to the connection pool with origin being origin and credentials being credentials.

6. Return connection.

This is intentionally a little vague as the finer points are still evolving. Describing this helps explain the <link rel=preconnect> feature and clearly stipulates that connections are keyed on credentials. The latter clarifies that e.g., TLS session identifiers are not reused across connections whose credentials are false with connections whose credentials are true.

2.6. HTTP cache partitions

To determine the HTTP cache partition, given request, run these steps:

1. Let topLevelOrigin be null.

2. If request’s reserved client is non-null, then:

   1. Set topLevelOrigin to request’s reserved client’s top-level origin.

   2. If topLevelOrigin is null, then set topLevelOrigin to request’s reserved client’s top-level creation URL’s origin.

      This happens for top-level navigations only.

3. Otherwise, if request’s client is non-null, set topLevelOrigin to request’s client’s top-level origin.

4. Otherwise, return null.

5. Assert: topLevelOrigin is an origin.

6. Let topLevelSite be the result of obtaining a site, given topLevelOrigin.

7. Return the HTTP cache associated with topLevelSite and, possibly, a second key. [HTTP-CACHING]

   The second key is intentionally a little vague as the finer points are still evolving. See issue #1035.

2.7. Port blocking

To determine whether fetching a request request should be blocked due to a bad port, run these steps:

1. Let url be request’s current URL.

2. Let scheme be url’s scheme.

3. Let port be url’s port.

4. If scheme is "ftp" and port is 20 or 21, then return allowed.

5. Otherwise, if scheme is a network scheme and port is a bad port, then return blocked.

6. Return allowed.

A port is a bad port if it is listed in the first column of the following table.

2.8. Should response to request be blocked due to its MIME type?

Run these steps:

1. Let mimeType be the result of extracting a MIME type from response’s header list.

2. If mimeType is failure, then return allowed.

3. Let destination be request’s destination.

4. If destination is script-like and one of the following is true, then return blocked:

   • mimeType’s essence starts with "audio/", "image/", or "video/".
   • mimeType’s essence is "text/csv".

5. Return allowed.

2.9. Streams

This section might be integrated into other standards, such as Streams itself. See whatwg/streams#372.

In this section, we define common operations for ReadableStream objects. [STREAMS]

To enqueue chunk into a ReadableStream object stream, run these steps:

1. Call ReadableStreamDefaultControllerEnqueue(stream.[[readableStreamController]], chunk).

To close a ReadableStream object stream, run these steps:

1. Call ReadableStreamDefaultControllerClose(stream.[[readableStreamController]]).

To error a ReadableStream object stream with given reason, run these steps:

1. Call ReadableStreamDefaultControllerError(stream.[[readableStreamController]]), reason).

To construct a ReadableStream object optionally with a highWaterMark, sizeAlgorithm algorithm, pull action, and cancel action, run these steps:

1. Let startAlgorithm be an algorithm that returns undefined.

2. If pull is not given, then set it to an action that does nothing.

3. Let pullAlgorithm be an algorithm that runs these steps:

   1. Run pull.

   2. Return a promise resolved with undefined.

4. If cancel is not given, then set it to an action that does nothing.

5. Let cancelAlgorithm be an algorithm that runs these steps:

   1. Run cancel.

   2. Return a promise resolved with undefined.

6. If highWaterMark is not given, then set it to 1.

7. If sizeAlgorithm is not given, then set it to an algorithm that returns 1.

8. Return CreateReadableStream(startAlgorithm, pullAlgorithm, cancelAlgorithm, highWaterMark, sizeAlgorithm).

To construct a fixed ReadableStream object with given chunks, run these steps:

1. Let stream be the result of constructing a ReadableStream object.

2. For each chunk in chunks, enqueue chunk into stream.

3. Close stream.

4. Return stream.

To get a reader from a ReadableStream object stream, run these steps:

1. Let reader be the result of calling AcquireReadableStreamDefaultReader(stream).

2. Return reader.

To read a chunk from a ReadableStream object with reader, given a read request readRequest, perform ReadableStreamDefaultReaderRead(reader, readRequest).

To read all bytes from a ReadableStream object with reader, run these steps:

1. Let promise be a new promise.

2. Let bytes be an empty byte sequence.

3. Read-loop given reader, bytes, and promise.

4. Return promise.

To read-loop given reader, bytes, and promise:

1. Let readRequest be a new read request with the following items:

   chunk steps, given chunk

   1. Assert: chunk is a Uint8Array object.

   2. Append chunk to bytes.

   3. Read-loop given reader, bytes, and promise.

   close steps

   1. Resolve promise with bytes.

   error steps, given e

   1. Reject promise with e.

2. Perform ReadableStreamDefaultReaderRead(reader, readRequest).

Because the reader grants exclusive access, the actual mechanism of how to read cannot be observed. Implementations could use more direct mechanism if convenient.

To cancel a ReadableStream object stream with reason, return the result of calling ReadableStreamCancel(stream, reason).

To tee a ReadableStream object stream, run these steps:

1. Return the result of calling ReadableStreamTee(stream, true).

An empty ReadableStream object is the result of constructing a fixed ReadableStream object with an empty list.

Constructing an empty ReadableStream object will not throw an exception.

A ReadableStream object stream is said to be readable if stream.[[state]] is "readable".

A ReadableStream object stream is said to be closed if stream.[[state]] is "closed".

A ReadableStream object stream is said to be errored if stream.[[state]] is "errored".

A ReadableStream object stream is said to be locked if the result of calling IsReadableStreamLocked(stream) is true.

A ReadableStream object stream is said to need more data if the following conditions hold:

• stream is readable.

• The result of calling ReadableStreamDefaultControllerGetDesiredSize(stream.[[readableStreamController]]) is positive.

A ReadableStream object stream is said to be disturbed if the result of calling IsReadableStreamDisturbed(stream) is true.

3. HTTP extensions

3.1. `Origin` header

The `Origin` request header indicates where a fetch originates from.

The `Origin` header is a version of the `Referer` [sic] header that does not reveal a path. It is used for all HTTP fetches whose request’s response tainting is "cors", as well as those where request’s method is neither `GET` nor `HEAD`. Due to compatibility constraints it is not included in all fetches.

Its value ABNF:

Origin                           = origin-or-null

origin-or-null                   = origin / %s"null" ; case-sensitive
origin                           = scheme "://" host [ ":" port ]

This supplants the `Origin` header. [ORIGIN]

To append a request `Origin` header, given a request request, run these steps:

1. Let serializedOrigin be the result of byte-serializing a request origin with request.

2. If request’s response tainting is "cors" or request’s mode is "websocket", then append `Origin`/serializedOrigin to request’s header list.

3. Otherwise, if request’s method is neither `GET` nor `HEAD`, then:

   1. Switch on request’s referrer policy:

      "no-referrer"

      Set serializedOrigin to `null`.

      "no-referrer-when-downgrade"

      "strict-origin"

      "strict-origin-when-cross-origin"

      If request’s origin is a tuple origin, its scheme is "https", and request’s current URL’s scheme is not "https", then set serializedOrigin to `null`.

      "same-origin"

      If request’s origin is not same origin with request’s current URL’s origin, then set serializedOrigin to `null`.

      Otherwise

      Do nothing.

   2. Append `Origin`/serializedOrigin to request’s header list.

A request’s referrer policy is taken into account for all fetches where the fetcher did not explicitly opt into sharing their origin with the server, e.g., via using the CORS protocol.

3.2. CORS protocol

To allow sharing responses cross-origin and allow for more versatile fetches than possible with HTML’s form element, the CORS protocol exists. It is layered on top of HTTP and allows responses to declare they can be shared with other origins.

It needs to be an opt-in mechanism to prevent leaking data from responses behind a firewall (intranets). Additionally, for requests including credentials it needs to be opt-in to prevent leaking potentially-sensitive data.

This section explains the CORS protocol as it pertains to server developers. Requirements for user agents are part of the fetch algorithm, except for the new HTTP header syntax.

3.2.1. General

The CORS protocol consists of a set of headers that indicates whether a response can be shared cross-origin.

For requests that are more involved than what is possible with HTML’s form element, a CORS-preflight request is performed, to ensure request’s current URL supports the CORS protocol.

3.2.2. HTTP requests

A CORS request is an HTTP request that includes an `Origin` header. It cannot be reliably identified as participating in the CORS protocol as the `Origin` header is also included for all requests whose method is neither `GET` nor `HEAD`.

A CORS-preflight request is a CORS request that checks to see if the CORS protocol is understood. It uses `OPTIONS` as method and includes these headers:

`Access-Control-Request-Method`

Indicates which method a future CORS request to the same resource might use.

`Access-Control-Request-Headers`

Indicates which headers a future CORS request to the same resource might use.

3.2.3. HTTP responses

An HTTP response to a CORS request can include the following headers:

`Access-Control-Allow-Origin`

Indicates whether the response can be shared, via returning the literal value of the `Origin` request header (which can be `null`) or `*` in a response.

`Access-Control-Allow-Credentials`

Indicates whether the response can be shared when request’s credentials mode is "include".

For a CORS-preflight request, request’s credentials mode is always "omit", but for any subsequent CORS requests it might not be. Support therefore needs to be indicated as part of the HTTP response to the CORS-preflight request as well.

An HTTP response to a CORS-preflight request can include the following headers:

`Access-Control-Allow-Methods`

Indicates which methods are supported by the response’s URL for the purposes of the CORS protocol.

The `Allow` header is not relevant for the purposes of the CORS protocol.

`Access-Control-Allow-Headers`

Indicates which headers are supported by the response’s URL for the purposes of the CORS protocol.

`Access-Control-Max-Age`

Indicates the number of seconds (5 by default) the information provided by the `Access-Control-Allow-Methods` and `Access-Control-Allow-Headers` headers can be cached.

An HTTP response to a CORS request that is not a CORS-preflight request can also include the following header:

`Access-Control-Expose-Headers`

Indicates which headers can be exposed as part of the response by listing their names.

In case a server does not wish to participate in the CORS protocol, its HTTP response to the CORS or CORS-preflight request must not include any of the above headers. The server is encouraged to use the 403 status in such HTTP responses.

3.2.4. HTTP new-header syntax

ABNF for the values of the headers used by the CORS protocol:

Access-Control-Request-Method    = method
Access-Control-Request-Headers   = 1#field-name

wildcard                         = "*"
Access-Control-Allow-Origin      = origin-or-null / wildcard
Access-Control-Allow-Credentials = %s"true" ; case-sensitive
Access-Control-Expose-Headers    = #field-name
Access-Control-Max-Age           = delta-seconds
Access-Control-Allow-Methods     = #method
Access-Control-Allow-Headers     = #field-name

For `Access-Control-Expose-Headers`, `Access-Control-Allow-Methods`, and `Access-Control-Allow-Headers` response headers the value `*` counts as a wildcard for requests without credentials. For such requests there is no way to solely match a header name or method that is `*`.

3.2.5. CORS protocol and credentials

When request’s credentials mode is "include" it has an impact on the functioning of the CORS protocol other than including credentials in the fetch.

var client = new XMLHttpRequest()
client.open("GET", "./")
client.withCredentials = true
/* … */

A request’s credentials mode is not necessarily observable on the server; only when credentials exist for a request can it be observed by virtue of the credentials being included. Note that even so, a CORS-preflight request never includes credentials.

The server developer therefore needs to decide whether or not responses "tainted" with credentials can be shared. And also needs to decide if requests necessitating a CORS-preflight request can include credentials. Generally speaking, both sharing responses and allowing requests with credentials is rather unsafe, and extreme care has to be taken to avoid the confused deputy problem.

To share responses with credentials, the `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` headers are important. The following table serves to illustrate the various legal and illegal combinations for a request to https://rabbit.invalid/:

Similarly, `Access-Control-Expose-Headers`, `Access-Control-Allow-Methods`, and `Access-Control-Allow-Headers` response headers can only use `*` as value when request’s credentials mode is not "include".

3.2.6. Examples

var url = "https://bar.invalid/api?key=730d67a37d7f3d802e96396d00280768773813fbe726d116944d814422fc1a45&data=about:unicorn";
fetch(url).then(success, failure)

Origin: https://foo.invalid

fetch(url).then(response => {
  var hsts = response.headers.get("strict-transport-security"),
      csp = response.headers.get("content-security-policy")
  log(hsts, csp)
})

Content-Security-Policy: default-src 'self'
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
Access-Control-Expose-Headers: Content-Security-Policy

fetch(url, { credentials:"include" }).then(success, failure)

Access-Control-Allow-Origin: https://foo.invalid
Access-Control-Allow-Credentials: true

3.2.7. CORS protocol exceptions

Specifications have allowed limited exceptions to the CORS safelist for non-safelisted `Content-Type` header values. These exceptions are made for requests that can be triggered by web content but whose headers and bodies can be only minimally controlled by the web content. Therefore, servers should expect cross-origin web content to be allowed to trigger non-preflighted requests with the following non-safelisted `Content-Type` header values:

• `application/csp-report` [CSP]
• `application/expect-ct-report+json` [EXPECT-CT]
• `application/xss-auditor-report`
• `application/ocsp-request` [OCSP]

Specifications should avoid introducing new exceptions and should only do so with careful consideration for the security consequences. New exceptions can be proposed by filing an issue.

3.3. `Content-Type` header

The `Content-Type` header is largely defined in HTTP. Its processing model is defined here as the ABNF defined in HTTP is not compatible with web content. [HTTP]

To extract a MIME type from a header list headers, run these steps:

1. Let charset be null.

2. Let essence be null.

3. Let mimeType be null.

4. Let values be the result of getting, decoding, and splitting `Content-Type` from headers.

5. If values is null, then return failure.

6. For each value of values:

   1. Let temporaryMimeType be the result of parsing value.

   2. If temporaryMimeType is failure or its essence is "*/*", then continue.

   3. Set mimeType to temporaryMimeType.

   4. If mimeType’s essence is not essence, then:

      1. Set charset to null.

      2. If mimeType’s parameters["charset"] exists, then set charset to mimeType’s parameters["charset"].

      3. Set essence to mimeType’s essence.

   5. Otherwise, if mimeType’s parameters["charset"] does not exist, and charset is non-null, set mimeType’s parameters["charset"] to charset.

7. If mimeType is null, then return failure.

8. Return mimeType.

When extract a MIME type returns failure or a MIME type whose essence is incorrect for a given format, treat this as a fatal error. Existing web platform features have not always followed this pattern, which has been a major source of security vulnerabilities in those features over the years. In contrast, a MIME type’s parameters can typically be safely ignored.

Content-Type: text/plain;charset=gbk, text/html

Content-Type: text/html;charset=gbk;a=b, text/html;x=y

Content-Type: text/html;charset=gbk;a=b
Content-Type: text/html;x=y

Content-Type: text/html;charset=gbk
Content-Type: x/x
Content-Type: text/html;x=y

Content-Type: text/html
Content-Type: cannot-parse

Content-Type: text/html
Content-Type: */*

Content-Type: text/html
Content-Type:

3.4. `X-Content-Type-Options` header

The `X-Content-Type-Options` response header can be used to require checking of a response’s `Content-Type` header against the destination of a request.

To determine nosniff, given a header list list, run these steps:

1. Let values be the result of getting, decoding, and splitting `X-Content-Type-Options` from list.

2. If values is null, then return false.

3. If values[0] is an ASCII case-insensitive match for "nosniff", then return true.

4. Return false.

Web developers and conformance checkers must use the following value ABNF for `X-Content-Type-Options`:

X-Content-Type-Options           = "nosniff" ; case-insensitive

3.4.1. Should response to request be blocked due to nosniff?

Run these steps:

1. If determine nosniff with response’s header list is false, then return allowed.

2. Let mimeType be the result of extracting a MIME type from response’s header list.

3. Let destination be request’s destination.

4. If destination is script-like and mimeType is failure or is not a JavaScript MIME type, then return blocked.

5. If destination is "style" and mimeType is failure or its essence is not "text/css", then return blocked.

6. Return allowed.

Only request destinations that are script-like or "style" are considered as any exploits pertain to them. Also, considering "image" was not compatible with deployed content.

3.5. CORB

Cross-origin read blocking, better known as CORB, is an algorithm which identifies dubious cross-origin resource fetches (e.g., fetches that would fail anyway like attempts to render JSON inside an img element) and blocks them before they reach a web page. CORB reduces the risk of leaking sensitive data by keeping it further from cross-origin web pages.

A CORB-protected MIME type is an HTML MIME type, a JSON MIME type, or an XML MIME type excluding image/svg+xml.

Even without CORB, accessing the content of cross-origin resources with CORB-protected MIME types is either managed by the CORS protocol (e.g., in case of XMLHttpRequest), not observable (e.g., in case of pings or CSP reports which ignore the response), or would result in an error (e.g., when failing to decode an HTML document embedded in an img element as an image). This means that CORB can block CORB-protected MIME types resources without being disruptive to web pages.

To perform a CORB check, given a request and response, run these steps:

1. If request’s initiator is "download", then return allowed.

   If we recast downloading as navigation this step can be removed.

2. If request’s current URL’s scheme is not an HTTP(S) scheme, then return allowed.

3. Let mimeType be the result of extracting a MIME type from response’s header list.

4. If mimeType is failure, then return allowed.

5. If response’s status is 206 and mimeType is a CORB-protected MIME type, then return blocked.

6. If determine nosniff with response’s header list is true and mimeType is a CORB-protected MIME type or its essence is "text/plain", then return blocked.

   CORB only protects text/plain responses with a `X-Content-Type-Options: nosniff` header. Unfortunately, protecting such responses without that header when their status is 206 would break too many existing video responses that have a text/plain MIME type.

7. Return allowed.

3.6. `Cross-Origin-Resource-Policy` header

The `Cross-Origin-Resource-Policy` response header can be used to require checking a request’s current URL’s origin against a request’s origin when request’s mode is "no-cors".

Its value ABNF:

Cross-Origin-Resource-Policy     = %s"same-origin" / %s"same-site" / %s"cross-origin" ; case-sensitive

To perform a cross-origin resource policy check, given an origin origin, an environment settings object settingsObject, a response response, and an optional boolean forNavigation, run these steps:

1. Set forNavigation to false if it is not given.

2. Let embedderPolicy be settingsObject’s embedder policy.

3. If the cross-origin resource policy internal check with origin, "unsafe-none", response, and forNavigation returns blocked, then return blocked.

   This step is needed because we don’t want to report violations not related to Cross-Origin Embedder Policy below.

4. If the cross-origin resource policy internal check with origin, embedderPolicy’s report only value, response, and forNavigation returns blocked, then queue a cross-origin embedder policy CORP violation report with response, settingsObject, and true.

5. If the cross-origin resource policy internal check with origin, embedderPolicy’s value, response, and forNavigation returns allowed, then return allowed.

6. Queue a cross-origin embedder policy CORP violation report with response, settingsObject, and false.

7. Return blocked.

Only HTML’s navigate algorithm uses this check with forNavigation set to true, and it’s always for nested navigations. Otherwise, response is either the internal response of an opaque filtered response or a response which will be the internal response of an opaque filtered response. [HTML]

To perform a cross-origin resource policy internal check, given an origin origin, an embedder policy value embedderPolicyValue, a response response, and a boolean forNavigation, run these steps:

1. If forNavigation is true and embedderPolicyValue is "unsafe-none", then return allowed.

2. Let policy be the result of getting `Cross-Origin-Resource-Policy` from response’s header list.

   This means that `Cross-Origin-Resource-Policy: same-site, same-origin` ends up as allowed below as it will never match anything, as long as embedderPolicyValue is "unsafe-none". Two or more `Cross-Origin-Resource-Policy` headers will have the same effect.

3. If policy is neither `same-origin`, `same-site`, nor `cross-origin`, then set policy to null.

4. If policy is null and embedderPolicyValue is "require-corp", then set policy to `same-origin`.

5. Switch on policy:

   null

   `cross-origin`

   Return allowed.

   `same-origin`

   If origin is same origin with response’s URL’s origin, then return allowed.

   Otherwise, return blocked.

   `same-site`

   If the following are true

   • origin is schemelessly same site with response’s URL’s origin

   • origin’s scheme is "https" or response’s HTTPS state is "none"

   then return allowed.

   Otherwise, return blocked.

   `Cross-Origin-Resource-Policy: same-site` does not consider a response delivered via a secure transport to match a non-secure requesting origin, even if their hosts are otherwise same site. Securely-transported responses will only match a securely-transported initiator.

To queue a cross-origin embedder policy CORP violation report, given a response response, an environment settings object settingsObject, and a boolean reportOnly, run these steps:

1. Let endpoint be settingsObject’s embedder policy’s report only reporting endpoint if reportOnly is true and settingsObject’s embedder policy’s reporting endpoint otherwise.

2. Let serialized url be the result of serializing a response URL for reporting with response.

3. Let body be a new object containing the following properties:

   key	value
   "type"	"corp"
   "blocked-url"	serialized url

4. Queue body as the "coep" report type for endpoint on settingsObject. [REPORTING]

4. Fetching

To perform a fetch using request, run the steps below. An ongoing fetch can be terminated with flag aborted, which is unset unless otherwise specified.

The user agent may be asked to suspend the ongoing fetch. The user agent may either accept or ignore the suspension request. The suspended fetch can be resumed. The user agent should ignore the suspension request if the ongoing fetch is updating the response in the HTTP cache for the request.

The user agent does not update the entry in the HTTP cache for a request if request’s cache mode is "no-store" or a `Cache-Control: no-store` header appears in the response. [HTTP-CACHING]

1. Run these steps, but abort when the ongoing fetch is terminated:

   1. If request’s window is "client", set request’s window to request’s client, if request’s client’s global object is a Window object, and to "no-window" otherwise.

   2. If request’s origin is "client", set request’s origin to request’s client’s origin.

   3. If request’s header list does not contain `Accept`, then:

      1. Let value be `*/*`.

      2. A user agent should set value to the first matching statement, if any, switching on request’s destination:

         "document"

         "frame"

         "iframe"

         `text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8`

         "image"

         `image/png,image/svg+xml,image/*;q=0.8,*/*;q=0.5`

         "style"

         `text/css,*/*;q=0.1`

      3. Append `Accept`/value to request’s header list.

   4. If request’s header list does not contain `Accept-Language`, user agents should append `Accept-Language`/an appropriate value to request’s header list.

   5. If request’s priority is null, then use request’s initiator and destination appropriately in setting request’s priority to a user-agent-defined object.

      The user-agent-defined object could encompass stream weight and dependency for HTTP/2, and equivalent information used to prioritize dispatch and processing of HTTP/1 fetches.

   6. If request is a subresource request, then:

      1. Let record be a new fetch record consisting of request and this instance of the fetch algorithm.

      2. Append record to request’s client’s fetch group list of fetch records.

2. If aborted, then:

   1. Let aborted be the termination’s aborted flag.

   2. If aborted is set, then return an aborted network error.

   3. Return a network error.

3. Return the result of performing a main fetch using request.

4.1. Main fetch

To perform a main fetch using request, optionally with a recursive flag, run these steps:

When main fetch is invoked recursively recursive flag is set.

1. Let response be null.

2. Run these steps, but abort when the ongoing fetch is terminated:

   1. If request’s local-URLs-only flag is set and request’s current URL is not local, then set response to a network error.

   2. Execute Report Content Security Policy violations for request. [CSP]

   3. Upgrade request to a potentially secure URL, if appropriate. [UPGRADE]

   4. If should fetching request be blocked due to a bad port, should fetching request be blocked as mixed content, or should fetching request be blocked by Content Security Policy returns blocked, set response to a network error. [MIX] [CSP]

   5. If request’s referrer policy is the empty string and request’s client is non-null, then set request’s referrer policy to request’s client’s referrer policy. [REFERRER]

   6. If request’s referrer policy is the empty string, then set request’s referrer policy to "no-referrer-when-downgrade".

      We use "no-referrer-when-downgrade" because it is the historical default.

   7. If request’s referrer is not "no-referrer", set request’s referrer to the result of invoking determine request’s referrer. [REFERRER]

      As stated in Referrer Policy, user agents can provide the end user with options to override request’s referrer to "no-referrer" or have it expose less sensitive information.

   8. If request’s current URL’s scheme is "ftp", request’s client’s creation URL’s scheme is not "ftp", and request’s reserved client is either null or an environment whose target browsing context is a nested browsing context, then set response to a network error.

   9. Set request’s current URL’s scheme to "https" if all of the following conditions are true:

      • request’s current URL’s scheme is "http"
      • request’s current URL’s host is a domain
      • Matching request’s current URL’s host per Known HSTS Host Domain Name Matching results in either a superdomain match with an asserted includeSubDomains directive or a congruent match (with or without an asserted includeSubDomains directive). [HSTS]

3. If aborted, then:

   1. Let aborted be the termination’s aborted flag.

   2. If aborted is set, then return an aborted network error.

   3. Return a network error.

4. If request’s synchronous flag is unset and recursive flag is unset, run the remaining steps in parallel.

5. If response is null, then set response to the result of running the steps corresponding to the first matching statement:

   request’s current URL’s origin is same origin with request’s origin, and request’s response tainting is "basic"

   request’s current URL’s scheme is "data"

   request’s mode is "navigate" or "websocket"

   1. Set request’s response tainting to "basic".

   2. Return the result of performing a scheme fetch using request.

   HTML assigns any documents and workers created from URLs whose scheme is "data" a unique opaque origin. Service workers can only be created from URLs whose scheme is an HTTP(S) scheme. [HTML] [SW]

   request’s mode is "same-origin"

   Return a network error.

   request’s mode is "no-cors"

   1. If request’s redirect mode is not "follow", then return a network error.

   2. Set request’s response tainting to "opaque".

   3. Let noCorsResponse be the result of performing a scheme fetch using request.

   4. If noCorsResponse is a filtered response or the CORB check with request and noCorsResponse returns allowed, then return noCorsResponse.

   5. Return a new response whose status is noCorsResponse’s status, HTTPS state is noCorsResponse’s HTTPS state, and CSP list is noCorsResponse’s CSP list.

      This is only an effective defense against side channel attacks if noCorsResponse is kept isolated from the process that initiated the request.

   request’s current URL’s scheme is not an HTTP(S) scheme

   Return a network error.

   request’s use-CORS-preflight flag is set

   request’s unsafe-request flag is set and either request’s method is not a CORS-safelisted method or CORS-unsafe request-header names with request’s header list is not empty

   1. Set request’s response tainting to "cors".

   2. Let corsWithPreflightResponse be the result of performing an HTTP fetch using request with the CORS-preflight flag set.

   3. If corsWithPreflightResponse is a network error, then clear cache entries using request.

   4. Return corsWithPreflightResponse.

   Otherwise

   1. Set request’s response tainting to "cors".

   2. Return the result of performing an HTTP fetch using request.

6. If the recursive flag is set, return response.

7. If response is not a network error and response is not a filtered response, then:

   1. If request’s response tainting is "cors", then:

      1. Let headerNames be the result of extracting header list values given `Access-Control-Expose-Headers` and response’s header list.

      2. If request’s credentials mode is not "include" and headerNames contains `*`, then set response’s CORS-exposed header-name list to all unique header names in response’s header list.

      3. Otherwise, if headerNames is not null or failure, then set response’s CORS-exposed header-name list to headerNames.

         One of the headerNames can still be `*` at this point, but will only match a header whose name is `*`.

   2. Set response to the following filtered response with response as its internal response, depending on request’s response tainting:

      "basic"

      basic filtered response

      "cors"

      CORS filtered response

      "opaque"

      opaque filtered response

8. Let internalResponse be response, if response is a network error, and response’s internal response otherwise.

9. If internalResponse’s URL list is empty, then set it to a clone of request’s URL list.

   A response’s URL list can be empty (for example, when the response represents an about URL).

10. If request’s timing allow failed flag is unset, then set internalResponse’s timing allow passed flag.

11. Set internalResponse’s CSP list. [CSP]

12. If response is not a network error and any of the following algorithms returns blocked, then set response and internalResponse to a network error:

    • should internalResponse to request be blocked as mixed content [MIX]
    • should internalResponse to request be blocked by Content Security Policy [CSP]
    • should internalResponse to request be blocked due to its MIME type
    • should internalResponse to request be blocked due to nosniff

13. If response’s type is "opaque", internalResponse’s status is 206, internalResponse’s range-requested flag is set, and request’s header list does not contain `Range`, then set response and internalResponse to a network error.

    Traditionally, APIs accept a ranged response even if a range was not requested. This prevents a partial response from an earlier ranged request being provided to an API that did not make a range request.

    Further details

    The above steps prevent the following attack:

    A media element is used to request a range of a cross-origin HTML resource. Although this is invalid media, a reference to a clone of the response can be retained in a service worker. This can later be used as the response to a script element’s fetch. If the partial response is valid JavaScript (even though the whole resource is not), executing it would leak private data.

14. If response is not a network error and either request’s method is `HEAD` or `CONNECT`, or internalResponse’s status is a null body status, set internalResponse’s body to null and disregard any enqueuing toward it (if any).

    This standardizes the error handling for servers that violate HTTP.

15. If response is not a network error and request’s integrity metadata is not the empty string, then:

    1. Wait for response’s body.

    2. If response’s body’s stream has not errored, and response does not match request’s integrity metadata, set response and internalResponse to a network error. [SRI]

    This operates on response as this algorithm is not supposed to observe internalResponse. That would allow an attacker to use hashes as an oracle.

16. If request’s synchronous flag is set, wait for internalResponse’s body, and then return response.

    This terminates fetch.

17. If request’s current URL’s scheme is an HTTP(S) scheme, then:

    1. If request’s body is done, queue a fetch-request-done task for request.

    2. Otherwise, in parallel, wait for request’s body, and then queue a fetch-request-done task for request.

18. Queue a fetch task on request to process response for response.

19. Wait for internalResponse’s body.

20. Queue a fetch task on request to process response end-of-body for response.

21. Set request’s done flag.

22. Queue a fetch task on request to process response done for response.

4.2. Scheme fetch

To perform a scheme fetch using request, switch on request’s current URL’s scheme, and run the associated steps:

"about"

If request’s current URL’s cannot-be-a-base-URL flag is set and path contains a single string "blank", then return a new response whose status message is `OK`, header list consist of a single header whose name is `Content-Type` and value is `text/html;charset=utf-8`, body is the empty byte sequence, and HTTPS state is request’s client’s HTTPS state if request’s client is non-null.

Otherwise, return a network error.

URLs such as "about:config" are handled during navigation and result in a network error in the context of fetching.

"blob"

1. Run these steps, but abort when the ongoing fetch is terminated:

   1. Let blob be request’s current URL’s blob URL entry’s object.

   2. If request’s method is not `GET` or blob is not a Blob object, then return a network error. [FILEAPI]

      The `GET` method restriction serves no useful purpose other than being interoperable.

   3. Let response be a new response whose status message is `OK`.

   4. Append `Content-Length`/blob’s size attribute value to response’s header list.

   5. Append `Content-Type`/blob’s type attribute value to response’s header list.

   6. Set response’s HTTPS state to request’s client’s HTTPS state if request’s client is non-null.

   7. Set response’s body to the result of performing the read operation on blob.

   8. Return response.

2. If aborted, then:

   1. Let aborted be the termination’s aborted flag.

   2. If aborted is set, then return an aborted network error.

   3. Return a network error.

"data"

1. Let dataURLStruct be the result of running the data: URL processor on request’s current URL.

2. If dataURLStruct is failure, then return a network error.

3. Return a response whose status message is `OK`, header list consist of a single header whose name is `Content-Type` and value is dataURLStruct’s MIME type, serialized, body is dataURLStruct’s body, and HTTPS state is request’s client’s HTTPS state if request’s client is non-null.

"file"

For now, unfortunate as it is, file URLs are left as an exercise for the reader.

When in doubt, return a network error.

"ftp"

For now, unfortunate as it is, ftp URLs are mostly left as an exercise for the reader.

1. Let body be the result of the user agent obtaining content from request’s current URL from the network via FTP. [RFC959]

2. Let mime be `application/octet-stream`.

3. If body is the result of the user agent generating a directory listing page for the result of FTP’s LIST command, then set mime to `text/ftp-dir`.

4. Return a response whose status message is `OK`, header list consists of a single header whose name is `Content-Type` and whose value is mime, body is body, and HTTPS state is "none".

When in doubt, return a network error.

HTTP(S) scheme

Return the result of performing an HTTP fetch using request.

Otherwise

Return a network error.

4.3. HTTP fetch

To perform an HTTP fetch using request with an optional CORS-preflight flag, run these steps:

The CORS-preflight flag bookkeeping detail indicates a CORS-preflight request is needed.

1. Let response be null.

2. Let actualResponse be null.

3. If request’s service-workers mode is "all", then:

   1. Set response to the result of invoking handle fetch for request. [HTML] [SW]

   2. If response is not null, then:

      1. Transmit body for request.

      2. Set actualResponse to response, if response is not a filtered response, and to response’s internal response otherwise.

      3. If one of the following is true

         • response’s type is "error"

         • request’s mode is "same-origin" and response’s type is "cors"

         • request’s mode is not "no-cors" and response’s type is "opaque"

         • request’s redirect mode is not "manual" and response’s type is "opaqueredirect"
         • request’s redirect mode is not "follow" and response’s URL list has more than one item.

         then return a network error.

4. If response is null, then:

   1. If the CORS-preflight flag is set and one of these conditions is true:

      • There is no method cache entry match for request’s method using request, and either request’s method is not a CORS-safelisted method or request’s use-CORS-preflight flag is set.

      • There is at least one item in the CORS-unsafe request-header names with request’s header list for which there is no header-name cache entry match using request.

      Then:

      1. Let preflightResponse be the result of performing a CORS-preflight fetch using request.

      2. If preflightResponse is a network error, then return preflightResponse.

      This step checks the CORS-preflight cache and if there is no suitable entry it performs a CORS-preflight fetch which, if successful, populates the cache. The purpose of the CORS-preflight fetch is to ensure the fetched resource is familiar with the CORS protocol. The cache is there to minimize the number of CORS-preflight fetches.

   2. If request’s redirect mode is "follow", then set request’s service-workers mode to "none".

      Redirects coming from the network (as opposed to from a service worker) are not to be exposed to a service worker.

   3. Set response and actualResponse to the result of performing an HTTP-network-or-cache fetch using request.

   4. If request’s response tainting is "cors" and a CORS check for request and response returns failure, then return a network error.

      As the CORS check is not to be applied to responses whose status is 304 or 407, or responses from a service worker for that matter, it is applied here.

   5. If the TAO check for request and response returns failure, then set request’s timing allow failed flag.

5. If either request’s response tainting or response’s type is "opaque", and the cross-origin resource policy check with request’s origin, request’s client, and actualResponse returns blocked, then return a network error.

   The cross-origin resource policy check runs for responses coming from the network and responses coming from the service worker. This is different from the CORS check, as request’s client and the service worker can have different embedder policies.

6. If actualResponse’s status is a redirect status, then:

   1. If actualResponse’s status is not 303, request’s body is not null, and the connection uses HTTP/2, then user agents may, and are even encouraged to, transmit an RST_STREAM frame.

      303 is excluded as certain communities ascribe special status to it.

   2. Let location be the result of extracting header list values given `Location` and actualResponse’s header list.

   3. If location is a value, then set location to the result of parsing location with actualResponse’s URL.

   4. Set actualResponse’s location URL to location.

   5. Switch on request’s redirect mode:

      "error"

      Set response to a network error.

      "manual"

      Set response to an opaque-redirect filtered response whose internal response is actualResponse.

      "follow"

      Set response to the result of performing HTTP-redirect fetch using request and response.

7. Return response. Typically actualResponse’s body’s stream is still being enqueued to after returning.

4.4. HTTP-redirect fetch

This algorithm is used by HTML’s navigate algorithm in addition to HTTP fetch above. [HTML]

To perform an HTTP-redirect fetch using request and response, run these steps:

1. Let actualResponse be response, if response is not a filtered response, and response’s internal response otherwise.

2. If actualResponse’s location URL is null, then return response.

3. If actualResponse’s location URL is failure, then return a network error.

4. If actualResponse’s location URL’s scheme is not an HTTP(S) scheme, then return a network error.

5. If request’s redirect count is twenty, return a network error.

6. Increase request’s redirect count by one.

7. If request’s mode is "cors", actualResponse’s location URL includes credentials, and request’s origin is not same origin with actualResponse’s location URL’s origin, then return a network error.

8. If request’s response tainting is "cors" and actualResponse’s location URL includes credentials, then return a network error.

   This catches a cross-origin resource redirecting to a same-origin URL.

9. If actualResponse’s status is not 303, request’s body is non-null, and request’s body’s source is null, then return a network error.

10. If actualResponse’s location URL’s origin is not same origin with request’s current URL’s origin and request’s origin is not same origin with request’s current URL’s origin, then set request’s tainted origin flag.

11. If one of the following is true

    • actualResponse’s status is 301 or 302 and request’s method is `POST`

    • actualResponse’s status is 303 and request’s method is not `GET` or `HEAD`

    then:

    1. Set request’s method to `GET` and request’s body to null.

    2. For each headerName of request-body-header name, delete headerName from request’s header list.

12. If request’s body is non-null, then set request’s body to the first return value of safely extracting request’s body’s source.

    request’s body’s source’s nullity has already been checked.

13. Append actualResponse’s location URL to request’s URL list.

14. Invoke set request’s referrer policy on redirect on request and actualResponse. [REFERRER]

15. Return the result of performing a main fetch using request with recursive flag set if request’s redirect mode is not "manual".

    It can only be "manual" here when this algorithm is invoked directly from HTML’s navigate algorithm.

    This has to invoke main fetch to get response tainting correct.

4.5. HTTP-network-or-cache fetch

To perform an HTTP-network-or-cache fetch using request with an optional authentication-fetch flag, run these steps:

The authentication-fetch flag is a bookkeeping detail.

Some implementations might support caching of partial content, as per HTTP Range Requests. [HTTP-RANGE] However, this is not widely supported by browser caches.

1. Let httpRequest be null.

2. Let response be null.

3. Let storedResponse be null.

4. Let httpCache be null.

5. Let the revalidatingFlag be unset.

6. Run these steps, but abort when the ongoing fetch is terminated:

   1. If request’s window is "no-window" and request’s redirect mode is "error", then set httpRequest to request.

   2. Otherwise:

      1. Set httpRequest to a copy of request except for its body.

      2. Let body be request’s body.

      3. Set httpRequest’s body to body.

      4. If body is non-null, then set request’s body to a new body whose stream is null and whose source is body’s source.

      request is copied as httpRequest here as we need to be able to add headers to httpRequest and read its body without affecting request. Namely, request can be reused with redirects, authentication, and proxy authentication. We copy rather than clone in order to reduce memory consumption. In case request’s body’s source is null, redirects and authentication will end up failing the fetch.

   3. Let credentials flag be set if one of

      • request’s credentials mode is "include"
      • request’s credentials mode is "same-origin" and request’s response tainting is "basic"

      is true, and unset otherwise.

   4. Let contentLengthValue be null.

   5. If httpRequest’s body is null and httpRequest’s method is `POST` or `PUT`, then set contentLengthValue to `0`.

   6. If httpRequest’s body is non-null and httpRequest’s body’s source is non-null, then set contentLengthValue to httpRequest’s body’s total bytes, serialized and isomorphic encoded.

   7. If contentLengthValue is non-null, append `Content-Length`/contentLengthValue to httpRequest’s header list.

   8. If contentLengthValue is non-null and httpRequest’s keepalive flag is set, then:

      1. Let inflightKeepaliveBytes be zero.

      2. Let group be httpRequest’s client’s fetch group.

      3. Let inflightRecords be the set of fetch records in group whose request has its keepalive flag set and done flag unset.

      4. For each fetchRecord in inflightRecords:

         1. Let inflightRequest be fetchRecord’s request.

         2. Increment inflightKeepaliveBytes by inflightRequest’s body’s total bytes.

      5. If the sum of contentLengthValue and inflightKeepaliveBytes is greater than 64 kibibytes, then return a network error.

      The above limit ensures that requests that are allowed to outlive the environment settings object and contain a body, have a bounded size and are not allowed to stay alive indefinitely.

   9. If httpRequest’s referrer is a URL, then append `Referer`/httpRequest’s referrer, serialized and isomorphic encoded, to httpRequest’s header list.

   10. Append a request `Origin` header for httpRequest.

   11. If httpRequest’s header list does not contain `User-Agent`, then user agents should append `User-Agent`/default `User-Agent` value to httpRequest’s header list.

   12. If httpRequest’s cache mode is "default" and httpRequest’s header list contains `If-Modified-Since`, `If-None-Match`, `If-Unmodified-Since`, `If-Match`, or `If-Range`, then set httpRequest’s cache mode to "no-store".

   13. If httpRequest’s cache mode is "no-cache", httpRequest’s prevent no-cache cache-control header modification flag is unset, and httpRequest’s header list does not contain `Cache-Control`, then append `Cache-Control`/`max-age=0` to httpRequest’s header list.

   14. If httpRequest’s cache mode is "no-store" or "reload", then:

       1. If httpRequest’s header list does not contain `Pragma`, then append `Pragma`/`no-cache` to httpRequest’s header list.

       2. If httpRequest’s header list does not contain `Cache-Control`, then append `Cache-Control`/`no-cache` to httpRequest’s header list.

   15. If httpRequest’s header list contains `Range`, then append `Accept-Encoding`/`identity` to httpRequest’s header list.

       This avoids a failure when handling content codings with a part of an encoded response.

       Additionally, many servers mistakenly ignore `Range` headers if a non-identity encoding is accepted.

   16. Modify httpRequest’s header list per HTTP. Do not append a given header if httpRequest’s header list contains that header’s name.

       It would be great if we could make this more normative somehow. At this point headers such as `Accept-Encoding`, `Connection`, `DNT`, and `Host`, are to be appended if necessary.

       `Accept`, `Accept-Charset`, and `Accept-Language` must not be included at this point.

       `Accept` and `Accept-Language` are already included (unless fetch() is used, which does not include the latter by default), and `Accept-Charset` is a waste of bytes. See HTTP header layer division for more details.

   17. If credentials flag is set, then:

       1. If the user agent is not configured to block cookies for httpRequest (see section 7 of [COOKIES]), then:

          1. Let cookies be the result of running the "cookie-string" algorithm (see section 5.4 of [COOKIES]) with the user agent’s cookie store and httpRequest’s current URL.

          2. If cookies is not the empty string, append `Cookie`/cookies to httpRequest’s header list.

       2. If httpRequest’s header list does not contain `Authorization`, then:

          1. Let authorizationValue be null.

          2. If there’s an authentication entry for httpRequest and either httpRequest’s use-URL-credentials flag is unset or httpRequest’s current URL does not include credentials, then set authorizationValue to authentication entry.

          3. Otherwise, if httpRequest’s current URL does include credentials and authentication-fetch flag is set, set authorizationValue to httpRequest’s current URL, converted to an `Authorization` value.

          4. If authorizationValue is non-null, then append `Authorization`/authorizationValue to httpRequest’s header list.

   18. If there’s a proxy-authentication entry, use it as appropriate.

       This intentionally does not depend on httpRequest’s credentials mode.

   19. Set httpCache to the result of determining the HTTP cache partition, given httpRequest.

   20. If httpCache is null, then set httpRequest’s cache mode to "no-store".

   21. If httpRequest’s cache mode is neither "no-store" nor "reload", then:

       1. Set storedResponse to the result of selecting a response from the httpCache, possibly needing validation, as per the "Constructing Responses from Caches" chapter of HTTP Caching [HTTP-CACHING], if any.

          As mandated by HTTP, this still takes the `Vary` header into account.

       2. If storedResponse is non-null, then:

          1. If cache mode is "default", storedResponse is a stale-while-revalidate response, and httpRequest’s client is non-null, then:

             1. Set response to storedResponse.

             2. Set response’s cache state to "local".

             3. Let revalidateRequest be a clone of request.

             4. Set revalidateRequest’s cache mode set to "no-cache".

             5. Set revalidateRequest’s prevent no-cache cache-control header modification flag.

             6. Set revalidateRequest’s service-workers mode set to "none".

             7. In parallel, perform main fetch using revalidateRequest.

                This fetch is only meant to update the state of httpCache and the response will be unused until another cache access. The stale response will be used as the response to current request. This fetch is issued in the context of a client so if it goes away the request will be terminated.

          2. Otherwise:

             1. If storedResponse is a stale response, then set the revalidatingFlag.

             2. If the revalidatingFlag is set and httpRequest’s cache mode is neither "force-cache" nor "only-if-cached", then:

                1. If storedResponse’s header list contains `ETag`, then append `If-None-Match` with its value to httpRequest’s header list.

                2. If storedResponse’s header list contains `Last-Modified`, then append `If-Modified-Since` with its value to httpRequest’s header list.

                See also the "Sending a Validation Request" chapter of HTTP Caching [HTTP-CACHING].

             3. Otherwise, set response to storedResponse and set response’s cache state to "local".

7. If aborted, then:

   1. Let aborted be the termination’s aborted flag.

   2. If aborted is set, then return an aborted network error.

   3. Return a network error.

8. If response is null, then:

   1. If httpRequest’s cache mode is "only-if-cached", then return a network error.

   2. Let forwardResponse be the result of making an HTTP-network fetch using httpRequest with credentials flag if set.

   3. If httpRequest’s method is unsafe and forwardResponse’s status is in the range 200 to 399, inclusive, invalidate appropriate stored responses in httpCache, as per the "Invalidation" chapter of HTTP Caching, and set storedResponse to null. [HTTP-CACHING]

   4. If the revalidatingFlag is set and forwardResponse’s status is 304, then:

      1. Update storedResponse’s header list using forwardResponse’s header list, as per the "Freshening Stored Responses upon Validation" chapter of HTTP Caching. [HTTP-CACHING]

         This updates the stored response in cache as well.

      2. Set response to storedResponse.

   5. If response is null, then:

      1. Set response to forwardResponse.

      2. Store httpRequest and forwardResponse in httpCache, as per the "Storing Responses in Caches" chapter of HTTP Caching. [HTTP-CACHING]

         If forwardResponse is a network error, this effectively caches the network error, which is sometimes known as "negative caching".

9. Set response’s URL list to a clone of httpRequest’s URL list.

10. If httpRequest’s header list contains `Range`, then set response’s range-requested flag.

11. If response’s status is 401, httpRequest’s response tainting is not "cors", the credentials flag is set, and request’s window is an environment settings object, then:

    1. Needs testing: multiple `WWW-Authenticate` headers, missing, parsing issues.

    2. If request’s body is non-null, then:

       1. If request’s body’s source is null, then return a network error.

       2. Set request’s body to the first return value of safely extracting request’s body’s source.

    3. If request’s use-URL-credentials flag is unset or authentication-fetch flag is set, then:

       1. If the ongoing fetch is terminated, then:

          1. Let aborted be the termination’s aborted flag.

          2. If aborted is set, then return an aborted network error.

          3. Return a network error.

       2. Let username and password be the result of prompting the end user for a username and password, respectively, in request’s window.

       3. Set the username given request’s current URL and username.

       4. Set the password given request’s current URL and password.

    4. Set response to the result of performing an HTTP-network-or-cache fetch using request with authentication-fetch flag set.

12. If response’s status is 407, then:

    1. If request’s window is "no-window", then return a network error.

    2. Needs testing: multiple `Proxy-Authenticate` headers, missing, parsing issues.

    3. If the ongoing fetch is terminated, then:

       1. Let aborted be the termination’s aborted flag.

       2. If aborted is set, then return an aborted network error.

       3. Return a network error.

    4. Prompt the end user as appropriate in request’s window and store the result as a proxy-authentication entry. [HTTP-AUTH]

       Remaining details surrounding proxy authentication are defined by HTTP.

    5. Set response to the result of performing an HTTP-network-or-cache fetch using request.

13. If authentication-fetch flag is set, then create an authentication entry for request and the given realm.

14. Return response. Typically response’s body’s stream is still being enqueued to after returning.

4.6. HTTP-network fetch

To perform an HTTP-network fetch using request with an optional credentials flag, run these steps:

1. Let credentials be true if credentials flag is set, and false otherwise.

2. Let response be null.

3. Let httpCache be the result of determining the HTTP cache partition, given httpRequest.

4. If httpCache is null, then set request’s cache mode to "no-store".

5. Switch on request’s mode:

   "websocket"

   Let connection be the result of obtaining a WebSocket connection, given request’s current URL.

   Otherwise

   Let connection be the result of obtaining a connection, given request’s current URL’s origin and credentials.

6. Run these steps, but abort when the ongoing fetch is terminated:

   1. If connection is failure, return a network error.

   2. If connection is not an HTTP/2 connection, request’s body is non-null, and request’s body’s source is null, then append `Transfer-Encoding`/`chunked` to request’s header list.

   3. Set response to the result of making an HTTP request over connection using request with the following caveats:

      • Follow the relevant requirements from HTTP. [HTTP] [HTTP-SEMANTICS] [HTTP-COND] [HTTP-CACHING] [HTTP-AUTH]

      • Wait until all the headers are transmitted.

      • Any responses whose status is in the range 100 to 199, inclusive, and is not 101, are to be ignored.

        These kind of responses are eventually followed by a "final" response.

      The exact layering between Fetch and HTTP still needs to be sorted through and therefore response represents both a response and an HTTP response here.

      If request’s header list contains `Transfer-Encoding`/`chunked` and response is transferred via HTTP/1.0 or older, then return a network error.

      If the HTTP request results in a TLS client certificate dialog, then:

      1. If request’s window is an environment settings object, make the dialog available in request’s window.

      2. Otherwise, return a network error.

      If response was retrieved over HTTPS, set its HTTPS state to either "deprecated" or "modern". [TLS]

      The exact determination here is up to user agents for the time being. User agents are strongly encouraged to only succeed HTTPS connections with strong security properties and return network errors otherwise. Using the "deprecated" state value ought to be a temporary and last resort kind of option.

      Transmit body for request.

7. If aborted, then:

   1. Let aborted be the termination’s aborted flag.

   2. If connection uses HTTP/2, then transmit an RST_STREAM frame.

   3. If aborted is set, then return an aborted network error.

   4. Return a network error.

8. Let highWaterMark be a non-negative, non-NaN number, chosen by the user agent.

9. Let sizeAlgorithm be an algorithm that accepts a chunk object and returns a non-negative, non-NaN, non-infinite number, chosen by the user agent.

10. Let pull be an action that resumes the ongoing fetch if it is suspended.

11. Let cancel be an action that terminates the ongoing fetch with the aborted flag set.

12. Let stream be the result of constructing a ReadableStream object with highWaterMark, sizeAlgorithm, pull, and cancel.

    This construction operation will not throw an exception.

13. Run these steps, but abort when the ongoing fetch is terminated:

    1. Set response’s body to a new body whose stream is stream.

    2. If response has a payload body length, then set response’s body’s total bytes to that payload body length.

    3. If response is not a network error and request’s cache mode is not "no-store", then update response in httpCache for request.

    4. If credentials flag is set and the user agent is not configured to block cookies for request (see section 7 of [COOKIES]), then run the "set-cookie-string" parsing algorithm (see section 5.2 of [COOKIES]) on the value of each header whose name is a byte-case-insensitive match for `Set-Cookie` in response’s header list, if any, and request’s current URL.

       This is a fingerprinting vector.

14. If aborted, then:

    1. Let aborted be the termination’s aborted flag.

    2. If aborted is set, then set response’s aborted flag.

    3. Return response.

15. Run these steps in parallel:

    1. Run these steps, but abort when the ongoing fetch is terminated:

       1. While true:

          1. If one or more bytes have been transmitted from response’s message body, then:

             1. Let bytes be the transmitted bytes.

             2. Increase response’s body’s transmitted bytes with bytes’ length.

             3. Let codings be the result of extracting header list values given `Content-Encoding` and response’s header list.

             4. Set bytes to the result of handling content codings given codings and bytes.

                This makes the `Content-Length` header unreliable to the extent that it was reliable to begin with.

             5. If bytes is failure, then terminate the ongoing fetch.

             6. Enqueue a Uint8Array object wrapping an ArrayBuffer containing bytes to stream. If that threw an exception, terminate the ongoing fetch, and error stream with that exception.

             7. If stream doesn’t need more data and request’s synchronous flag is unset, ask the user agent to suspend the ongoing fetch.

          2. Otherwise, if the bytes transmission for response’s message body is done normally and stream is readable, then close stream and abort these in-parallel steps.

    2. If aborted, then:

       1. Let aborted be the termination’s aborted flag.

       2. If aborted is set, then:

          1. Set response’s aborted flag.

          2. If stream is readable, error stream with an "AbortError" DOMException.

       3. Otherwise, if stream is readable, error stream with a TypeError.

       4. If connection uses HTTP/2, then transmit an RST_STREAM frame.

       5. Otherwise, the user agent should close connection unless it would be bad for performance to do so.

          For instance, the user agent could keep the connection open if it knows there’s only a few bytes of transfer remaining on a reusable connection. In this case it could be worse to close the connection and go through the handshake process again for the next fetch.

    These are run in parallel as at this point it is unclear whether response’s body is relevant (response might be a redirect).

16. Return response. Typically response’s body’s stream is still being enqueued to after returning.

4.7. CORS-preflight fetch

This is effectively the user agent implementation of the check to see if the CORS protocol is understood. The so-called CORS-preflight request. If successful it populates the CORS-preflight cache to minimize the number of these fetches.

To perform a CORS-preflight fetch using request, run these steps:

1. Let preflight be a new request whose method is `OPTIONS`, URL is request’s current URL, initiator is request’s initiator, destination is request’s destination, origin is request’s origin, referrer is request’s referrer, referrer policy is request’s referrer policy, mode is "cors", tainted origin flag is request’s tainted origin flag, and response tainting is "cors".

   The service-workers mode of preflight does not matter as this algorithm uses HTTP-network-or-cache fetch rather than HTTP fetch.

2. Append `Accept`/`*/*` to preflight’s header list.

3. Append `Access-Control-Request-Method`/request’s method to preflight’s header list.

4. Let headers be the CORS-unsafe request-header names with request’s header list.

5. If headers is not empty, then:

   1. Let value be the items in headers separated from each other by `,`.

   2. Append `Access-Control-Request-Headers`/value to preflight’s header list.

   This intentionally does not use combine, as 0x20 following 0x2C is not the way this was implemented, for better or worse.

6. Let response be the result of performing an HTTP-network-or-cache fetch using preflight.

7. If a CORS check for request and response returns success and response’s status is an ok status, then:

   The CORS check is done on request rather than preflight to ensure the correct credentials mode is used.

   1. Let methods be the result of extracting header list values given `Access-Control-Allow-Methods` and response’s header list.

   2. Let headerNames be the result of extracting header list values given `Access-Control-Allow-Headers` and response’s header list.

   3. If either methods or headerNames is failure, return a network error.

   4. If methods is null and request’s use-CORS-preflight flag is set, then set methods to a new list containing request’s method.

      This ensures that a CORS-preflight fetch that happened due to request’s use-CORS-preflight flag being set is cached.

   5. If request’s method is not in methods, request’s method is not a CORS-safelisted method, and request’s credentials mode is "include" or methods does not contain `*`, then return a network error.

   6. If one of request’s header list’s names is a CORS non-wildcard request-header name and is not a byte-case-insensitive match for an item in headerNames, then return a network error.

   7. For each unsafeName in the CORS-unsafe request-header names with request’s header list, if unsafeName is not a byte-case-insensitive match for an item in headerNames and request’s credentials mode is "include" or headerNames does not contain `*`, return a network error.

   8. Let max-age be the result of extracting header list values given `Access-Control-Max-Age` and response’s header list.

   9. If max-age is failure or null, then set max-age to 5.

   10. If max-age is greater than an imposed limit on max-age, then set max-age to the imposed limit.

   11. If the user agent does not provide for a cache, then return response.

   12. For each method in methods for which there is a method cache entry match using request, set matching entry’s max-age to max-age.

   13. For each method in methods for which there is no method cache entry match using request, create a new cache entry with request, max-age, method, and null.

   14. For each headerName in headerNames for which there is a header-name cache entry match using request, set matching entry’s max-age to max-age.

   15. For each headerName in headerNames for which there is no header-name cache entry match using request, create a new cache entry with request, max-age, null, and headerName.

   16. Return response.

8. Otherwise, return a network error.

4.8. CORS-preflight cache

A user agent has an associated CORS-preflight cache. A CORS-preflight cache is a list of cache entries.

A cache entry consists of:

• byte-serialized origin (a byte sequence)
• URL (a URL)
• max-age (a number of seconds)
• credentials (a boolean)
• method (null, `*`, or a method)
• header name (null, `*`, or a header name)

Cache entries must be removed after the seconds specified in their max-age field have passed since storing the entry. Cache entries may be removed before that moment arrives.

To create a new cache entry, given request, max-age, method, and headerName, run these steps:

1. Let entry be a cache entry, initialized as follows:

   byte-serialized origin

   The result of byte-serializing a request origin with request

   URL

   request’s current URL

   max-age

   max-age

   credentials

   True if request’s credentials mode is "include", and false otherwise

   method

   method

   header name

   headerName

2. Append entry to the user agent’s CORS-preflight cache.

To clear cache entries, given a request, remove any cache entries in the user agent’s CORS-preflight cache whose byte-serialized origin is the result of byte-serializing a request origin with request and whose URL is request’s current URL.

There is a cache entry match for a cache entry entry with request if entry’s byte-serialized origin is the result of byte-serializing a request origin with request, entry’s URL is request’s current URL, and one of

• entry’s credentials is true
• entry’s credentials is false and request’s credentials mode is not "include".

is true.

There is a method cache entry match for method using request when there is a cache entry in the user agent’s CORS-preflight cache for which there is a cache entry match with request and its method is method or `*`.

There is a header-name cache entry match for headerName using request when there is a cache entry in the user agent’s CORS-preflight cache for which there is a cache entry match with request and one of

• its header name is a byte-case-insensitive match for headerName
• its header name is `*` and headerName is not a CORS non-wildcard request-header name

is true.

4.9. CORS check

To perform a CORS check for a request and response, run these steps:

1. Let origin be the result of getting `Access-Control-Allow-Origin` from response’s header list.

2. If origin is null, then return failure.

   Null is not `null`.

3. If request’s credentials mode is not "include" and origin is `*`, then return success.

4. If the result of byte-serializing a request origin with request is not origin, then return failure.

5. If request’s credentials mode is not "include", then return success.

6. Let credentials be the result of getting `Access-Control-Allow-Credentials` from response’s header list.

7. If credentials is `true`, then return success.

8. Return failure.

4.10. TAO check

To perform a TAO check for a request and response, run these steps:

1. If request’s timing allow failed flag is set, then return failure.

2. If request’s response tainting is "basic", then return success.

3. Let values be the result of getting, decoding, and splitting `Timing-Allow-Origin` from response’s header list.

4. If values contains "*", then return success.

5. If values contains the result of serializing a request origin with request, then return success.

6. Return failure.

5. Fetch API

The fetch() method is relatively low-level API for fetching resources. It covers slightly more ground than XMLHttpRequest, although it is currently lacking when it comes to request progression (not response progression).

fetch("/music/pk/altes-kamuffel.flac")
  .then(res => res.blob()).then(playBlob)

fetch("/", {method:"HEAD"})
  .then(res => log(res.headers.get("strict-transport-security")))

fetch("https://pk.example/berlin-calling.json", {mode:"cors"})
  .then(res => {
    if(res.headers.get("content-type") &&
       res.headers.get("content-type").toLowerCase().indexOf("application/json") >= 0) {
      return res.json()
    } else {
      throw new TypeError()
    }
  }).then(processJSON)

var url = new URL("https://geo.example.org/api"),
    params = {lat:35.696233, long:139.570431}
Object.keys(params).forEach(key => url.searchParams.append(key, params[key]))
fetch(url).then(/* … */)

function consume(reader) {
  var total = 0
  return pump()
  function pump() {
    return reader.read().then(({done, value}) => {
      if (done) {
        return
      }
      total += value.byteLength
      log(`received ${value.byteLength} bytes (${total} bytes in total)`)
      return pump()
    })
  }
}

fetch("/music/pk/altes-kamuffel.flac")
  .then(res => consume(res.body.getReader()))
  .then(() => log("consumed the entire body without keeping the whole thing in memory!"))
  .catch(e => log("something went wrong: " + e))

5.1. Headers class

typedef (sequence<sequence<ByteString>> or record<ByteString, ByteString>) HeadersInit;

[Exposed=(Window,Worker)]
interface Headers {
  constructor(optional HeadersInit init);

  void append(ByteString name, ByteString value);
  void delete(ByteString name);
  ByteString? get(ByteString name);
  boolean has(ByteString name);
  void set(ByteString name, ByteString value);
  iterable<ByteString, ByteString>;
};

Unlike a header list, a Headers object cannot represent more than one `Set-Cookie` header. In a way this is problematic as unlike all other headers `Set-Cookie` headers cannot be combined, but since `Set-Cookie` headers are not exposed to client-side JavaScript this is deemed an acceptable compromise. Implementations could chose the more efficient Headers object representation even for a header list, as long as they also support an associated data structure for `Set-Cookie` headers.

var meta = { "Content-Type": "text/xml", "Breaking-Bad": "<3" }
new Headers(meta)

// The above is equivalent to
var meta = [
  [ "Content-Type", "text/xml" ],
  [ "Breaking-Bad", "<3" ]
]
new Headers(meta)

A Headers object has an associated header list (a header list), which is initially empty. This can be a pointer to the header list of something else, e.g., of a request as demonstrated by Request objects.

A Headers object also has an associated guard, which is "immutable", "request", "request-no-cors", "response" or "none".

To append a name/value name/value pair to a Headers object (headers), run these steps:

1. Normalize value.

2. If name is not a name or value is not a value, then throw a TypeError.

3. If headers’s guard is "immutable", then throw a TypeError.

4. Otherwise, if headers’s guard is "request" and name is a forbidden header name, return.

5. Otherwise, if headers’s guard is "request-no-cors":

   1. Let temporaryValue be the result of getting name from headers’s header list.

   2. If temporaryValue is null, then set temporaryValue to value.

   3. Otherwise, set temporaryValue to temporaryValue, followed by 0x2C 0x20, followed by value.

   4. If name/temporaryValue is not a no-CORS-safelisted request-header, then return.

6. Otherwise, if headers’s guard is "response" and name is a forbidden response-header name, return.

7. Append name/value to headers’s header list.

8. If headers’s guard is "request-no-cors", then remove privileged no-CORS request headers from headers.

To fill a Headers object headers with a given object object, run these steps:

1. If object is a sequence, then for each header in object:

   1. If header does not contain exactly two items, then throw a TypeError.

   2. Append header’s first item/header’s second item to headers.

2. Otherwise, object is a record, then for each key → value in object, append key/value to headers.

To remove privileged no-CORS request headers from a Headers object (headers), run these steps:

1. For each headerName of privileged no-CORS request-header names:

   1. Delete headerName from headers’s header list.

This is called when headers are modified by unprivileged code.

The new Headers(init) constructor steps are:

1. Set this’s guard to "none".

2. If init is given, then fill this with init.